Gitolite Essentials by 2014

Author:2014
Language: eng
Format: mobi
Publisher: Packt Publishing

Rule accumulation and delegation

Gitolite allows you to split up access rules for repositories into multiple chunks which are not necessarily contiguous. It will then combine all these chunks (in the order they were read) and apply the combined set of rules to the repository in question.

There's a very good use for this behavior. Combining groups, that include statement, and rule accumulation, makes Gitolite administration easier than it already is. Here's an example, with some comments, to give you some idea of what can be done.

include "groups.conf" # contains definitions of all groups used in the rest of the conf file. All # membership changes happen here include "foss.conf" # contains rules for open source repositories. For example, "R = @all" is # pretty much expected for such repositories. There may be other rules # specific to different FOSS repositories that may also be specified here include "boss.conf" # contains rules that define what kind of access management has to the # development repositories. For example, some of the managers may have # read access to all repositories, so something like # repo @all # R = scott douglas # is probably quite useful. # repo-specific rules # At this point you could have repository specific rules that do not fit neatly # into any of the previous include files. For example: repo git RW+ = linus junio

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.